Methods and apparatus to provide messages to television users

ABSTRACT

Methods and apparatus to provide messages to television users are disclosed. An example method includes receiving a request for a voicemail message from the television user, determining a voicemail mailbox associated with the television user, and sending at least one of a list of one or more voicemail messages or a voicemail message to a display device associated with the television user.

FIELD OF THE DISCLOSURE

This disclosure relates generally to communication systems and, moreparticularly, to methods and apparatus to provide messages to televisionusers.

BACKGROUND

Media users typically subscribe to multiple media and messaging services(e.g., television services, telephone services (land line and/orcellular), voice over internet protocol (VoIP) services, instantmessaging services, text messaging services, electronic mail (email)services, voicemail services, etc.). The media and messaging servicesmay be provided by a single media provider or may be provided bymultiple different providers. For example, a first provider may provideemail services while a second provider provides telephone services andtelevision services.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example system for presenting messagesto television users.

FIG. 2 is a block diagram of an example implementation of the mediationsystem of FIG. 1.

FIGS. 3 to 8 are a flowcharts representative of example machine readableinstructions that may be executed to implement the example mediationsystem of FIG. 1.

FIG. 9 illustrates an example data schema that illustrates how messagingaccounts may be linked to IPTV devices via an IPTV external identifier.

FIG. 10 is a block diagram of an example computer that may execute themachine readable instructions of FIGS. 3 to 8 to implement the examplesystem of FIG. 1.

DETAILED DESCRIPTION

Recently, multiple telecommunication services (e.g., VoIP services,internet protocol television (IPTV) services, etc.) have beencommunicatively linked together. By linking telecommunication services,notifications associated with one service can be transmitted to a uservia a second service. For example, notifications associated with a VoIPservice can be transmitted using an IPTV service. Example methods andapparatus for transmitting VoIP communication system notifications overan IPTV system are described in U.S. patent application Ser. Nos.11/287,147, 11/445,121, 11/400,906, and 11/561,944, which are herebyincorporated by reference.

FIG. 1 is a block diagram of an example system 100 for providingmessages to television users. In the illustrated example, messages(e.g., voicemail messages, text messages, electronic mail (email)messages, etc.) are transmitted to an internet protocol television(IPTV) system 110 for presentation to television users. For example,messages may be displayed on a television at a user location. Theexample system 100 includes a mediation system 106 to associate IPTVaccounts with associated accounts on other messaging services. Forexample, the mediation system 106 may associate a user's IPTV accountwith one or more of the user's email account(s), voicemail account(s),text messaging account(s), etc.

The example system 100 includes a user location 102, a network 104, aVoIP provider system 105, the mediation system 106, a messagingprovider(s) 108, and an IPTV system 110. Persons of ordinary skill inthe art will recognize that additional devices may be provided in theexample system 100. For example, the consumer location 102 may include acomputer and/or any other device connected to the network 104.

In the illustrated example, the user location 102 comprises aresidential gateway 102 a, an IPTV device 102 b, and a VoIP device 102c. The first user location may be a household, a business, a publicplace, or any other location where users can receive IPTV media content.Further, the user location may include more than one physical location.For example, the IPTV device 102 b need not be located near the VoIPdevice 102 c and/or both devices may be connected to differentresidential gateways (e.g., residential gateway 102 a and anotherresidential gateway (not shown)).

The residential gateway 102 a of the illustrated example is connected tothe network 104. The examples residential gateway 102 a sends data toand receives data from other devices connected to the network 104. Inthe illustrated example, the residential gateway 102 a sends internetprotocol data to and receives internet protocol data from the mediationsystem 106, the messaging provider(s) 108, the IPTV system 110, and/orany other device connected to the network 104 (e.g., a voice overinternet protocol (VoIP) provider system 105). In the illustratedexample, the residential gateway 102 a receives IPTV media content andmessages from the IPTV system 110. In addition, in the illustratedexample, the residential gateway 102 a sends requests for messages tothe mediation system 106 via the network 104 and the IPTV system 110 andreceives messages for display from the mediation system 106 via thenetwork 106 and the IPTV system 110.

The residential gateway 102 a of the illustrated example is implementedby an asynchronous digital subscriber line (ADSL) transmissionunit-remote (ATU-R). However, the residential gateway 102 a mayalternatively be implemented by a set top box, a cable modem, a dial-upmodem, or any other type of communication device. The residentialgateway 102 a may include IPTV reception capabilities and/or VoIPcapabilities. One or both of those functions (IPTV and/or VoIP) may beincluded in the same and/or separate devices (e.g., the IPTV device 102b and/or the VoIP device 102 c). In an alternate embodiment, theresidential gateway 102 a may be connected to an optical network unit(ONU) via its uplink Ethernet port if the access link is provided bygigabit-capable passive optical network (GPON)/fiber-to-the-premises(FTTP) technology.

The IPTV device 102 b of the illustrated example communicates with theIPTV system 110 via the residential gateway 102 a and the network 104 toreceive IPTV media content and/or messages. The IPTV device 102 b of theillustrated example includes a display for presenting the IPTV mediacontent and/or messages to users. Alternatively, a separate displaydevice may be connected to the IPTV device 102 b.

The IPTV device 102 b of the illustrated example receives messages fromthe IPTV system 110. For example, the IPTV device 102 b receivesmessages from the messaging provider(s) 108 via the mediation system106. A message may be a notification that new messages are waiting atthe messaging provider(s) 108, may be a message (e.g., a voicemail, atext message, an email) received by the messaging provider(s) 108, maybe a message associated with the IPTV system 110, or may be any othermessage.

The example IPTV device 102 b presents received messages to users. TheIPTV device 102 b of the illustrated example presents messages via aremote desktop protocol (RDP) connection to the IPTV system 110.Alternatively, the IPTV device 102 b may be implemented with HTTPapplications, such as Internet Explorer, and use HTTP to communicatewith the IPTV system 110. Received messages may be presented as adisplay of text, an audio presentation, a video presentation, etc. TheIPTV device 102 b may include the ability to convert messages from onepresentation type to another (e.g., from text to audio, from video toaudio, from text to video, from audio to text, from video to text,etc.).

The VoIP device 102 c of the illustrated example is capable ofinitiating and receiving VoIP communications. To this end, the exampleVoIP device 102 c connects to and authenticates with a VoIP providersystem 105. The VoIP provider system 105 is communicatively coupled tothe VoIP device 102 c via the network 104 and the residential gateway102 a. The example VoIP provider system 105 provides the capability tomake and receive VoIP communication session (phone calls). In addition,the VoIP provider system 105 may include a voicemail capability providedby a voicemail provider, which may be one of the messaging provider(s)108. The example VoIP device 102 c of FIG. 1 includes a phone adapterand handset. Alternatively, the VoIP device 102 c may be a handsetconnected to a VoIP capable residential gateway (e.g., residentialgateway 102 a), a router with VoIP capabilities connected to a handset,a personal computer executing software that provides VoIP capabilities,etc. Persons of ordinary skill in the art will recognize that additionalVoIP devices, like VoIP device 102 c, may be connected to the network104 through the RG 102 a or using any other type of connection.Additionally or alternatively, other communication devices such aspublic switch telephone network (PSTN) devices and/or time divisionmultiplexed (TDM) devices may be at the consumer location 102.

While the example system 100 of FIG. 1 includes a single user location102, any number of user locations may be associated with the system 100.In addition, the user locations associated with the system 100 mayinclude some or all of a residential gateway (e.g., residential gateway102 a), an IPTV device (e.g., IPTV device 102 b), a VoIP device (e.g.,VoIP device 102 c), and/or any other device(s). The user locations mayinclude other device such as, for example, cellular telephones, mobiletelephones, personal computers, laptop computers, plain old telephonesystem (POTS) telephones, etc. Some or all of the devices at the userlocation 102 may be associated with accounts at the messagingprovider(s) 108.

The network 104 of the illustrated example is a broadband communicationsnetwork. The network 104 may be implemented by one or more of any typeof local area network, wide area network, public network, privatenetwork, public switched telephone network, broadband network, and/orany other type of communication link.

The mediation system 106 of the illustrated example facilitatescommunication between the messaging provider(s) 108 and the IPTV system110. The example mediation system 106 receives requests for messaginginformation from the user location 102 via the network 104 and/or theIPTV system 110. The example mediation system 106 associates identifiersof IPTV users with identifiers for messaging provider(s) 108 and viceversa. In addition, the example mediation system sends messages andnotifications associated with the messaging provider(s) 108 to the userlocation 102 (e.g., the IPTV device 102 b) via the IPTV system 110 andthe network 104. The mediation system 106 of the illustrated exampleconverts messages from the messaging provider(s) 108 into messages thatare capable of being handled by the IPTV system 110. For example, themediation system 106 may convert a message that is formatted as aMicrosoft® Word document into a markup language format (e.g., ahypertext markup language (HTML), an extensible markup language (XML)format, simple object access, etc.). In another example, the mediationsystem 106 may convert an audio message into text using, for example, aspeech-to-text engine included in the mediation system 106. In anotherexample, the mediation system 106 may convert a video message from onevideo encoding format to another, may convert an audio message from oneaudio encoding format (e.g., Motion Pictures Expert Group (MPEG) layerthree (MP3)) to another, etc.

The IPTV system 110 of the illustrated example receives media contentfrom media content producers (e.g., television networks, movie studios,etc.) and transmits the media content to users (e.g., the user location102) via the example network 104. The example IPTV system 110 includesan IPTV notification sub-system 110 a. The IPTV notification sub-system110 a sends notification messages, alerts, etc. to IPTV users fordisplay on IPTV devices (e.g., the IPTV device 102 b). In theillustrated example, the IPTV notification sub-system 110 a receivesmessages including IPTV account information from the mediation system106 and transmits the notification messages to the IPTV devicesspecified by the IPTV account information. The example IPTV system 110may include other subsystems such as, for example, a remote terminalserver, a web application server, a web browser, etc. The IPTV system110 is described in further detail in U.S. patent application Ser. Nos.11/287,147, 11/445,121, 11/400,906, and 11/561,944, which have beenincorporated by reference.

FIG. 2 illustrates an example implementation of the mediation system 106of FIG. 1. The example mediation system 106 includes a messagingtransceiver 202, a notification receiver 204, a message converter 206, amessage presenter 208, a mediation database 210, a provider informationdatabase 212, a notification generator 214, a request receiver 216, andan administration interface 218.

The messaging transceiver 202 of the illustrated example sends requestsfor messages to the messaging provider(s) 108 of FIG. 1 and receivesmessages from the messaging provider(s) 108. The example messagingtransceiver 202 receives the requests for messages from television usersvia the request receiver 216. The example messaging transceiver 202sends messages received from the messaging provider(s) 108 to themessage converter 206. Alternatively, the messaging transceiver 202 maysend messages directly to the message presenter 208 if no messageconversion is desired.

The notification receiver 204 of the illustrated example receivesnotifications from the messaging provider(s) 108. In the illustratedexample, the notifications indicate that new messages are available atone or more of the messaging provider(s) 108. For example, if an emailmessaging provider receives a new email for a user that is configuredfor notification via the mediation system 106, the messaging providerwill send a notification to the notification receiver 204. Thenotification receiver 204 listens for notifications from the messagingprovider(s) 108. The messaging provider(s) 108 may be manuallyconfigured to send notifications to the notification receiver 205, thenotification receiver 205 may subscribe to notifications from themessaging provider(s) 108, or the messaging provider(s) 108 may beconfigured in any other method. Alternatively, the notification receiver204 may allow the messaging provider(s) 108 to access an applicationprogram interface (API) that allows the messaging provider(s) 108 toindicate that new messages are available. The notification receiver 204transmits notifications to the notification generator 214.

The message converter 206 of the illustrated example receives messagesfrom the messaging transceiver 202 and converts the messages to makethem suitable for presentation to users. The message converter 206 mayconvert the message between different encoding formats (e.g., from aMicrosoft® Word document to a plain text document, from a compressedformat to an uncompressed format, from a plain text document to a XMLdocument, from a plain text document to an HTML document, etc.), betweendifferent presentation formats (e.g., from text to speech, from speechto text, from video to audio, etc.), between different encoding formats(e.g., MP3, waveform audio format (WAV), Windows® media audio (WMA),etc.) between different display layouts (e.g., from a table to a columnof text, from a small font to a large font, from italicized to plain,etc.), or any other conversion. The message converter 206 sendsconverted messages to the message presenter 208.

The message presenter 208 of the illustrated example receives messagesfrom the message converter 206 (or from the message transceiver 202(e.g., if no message conversion is desired)) and generates a display forpresentation via the IPTV system 110 of FIG. 1. The example messagepresenter 208 may perform some format adjustments such as, for example,font size adjustment, font color adjustment, adjusting messagepositioning, etc.). For example, the message presenter 208 may generategraphical user interface (GUI) elements to provide the display (e.g.,scroll bars for scrolling through the text of the message, a text boxfor displaying the body of the messages, a text box for displaying theattributes of the message (e.g., subject, “to” field, “from” field,”etc.), etc. In addition, the message presenter 208 may adjust themessage to make it better suited for display. For example, the messagepresenter 208 may adjust the text of the body of a message to cause thetext to wrap so that it fits in a narrower text box than that for whichthe message was originally created. When the message is audio or video,the message presenter 208 may generate a GUI object that is capable ofpresenting the audio and/or video (e.g., a video player, an audioplayer, etc.). Alternatively, if the IPTV system 110 is capable ofhandling (e.g., receiving and sending to users for presentation) audioand/or video, the message presenter 208 may send the audio and videodirectly to the IPTV system 108. Alternatively, the example messageconverter 206 may include an interface to the provider informationdatabase 212 so that it may query the provider information database 212for directions/guidelines on how to handle message conversion.

To determine how messages should be converted, the message presenter 208of the illustrated example queries the provider information database 212for information about messages from the message provider(s) 108. Forexample, different message providers may store the same information indifferent fields or locations in a document. By querying the providerinformation database 212 with identity information associated with themessaging provider(s) 108, the message presenter 208 can receiveinformation describing messages from the messaging provider(s) 108.

In addition to generating display/presentation elements for messages,the message presenter 208 of the illustrated example, determines thedestination IPTV account for the messages. In the illustrated example,the message presenter 208 makes this determination by extractinginformation from the messages (e.g., the email account to which an emailwas addressed, the phone number or telephone account number to which avoicemail was addressed, etc.) and querying the mediation database 210to determine an IPTV account identifier associated with the destinationof the messages. Alternatively, the message presenter 208 may use anyother method to determine the intended IPTV account identifier addressassociated with a given message. In addition, a given message may beassociated with any number of IPTV accounts (e.g., a mobile phonevoicemail account may be associated with an IPTV account at a firstlocation and an IPTV account at a second location). Accordingly, themessage presenter 208 is capable of determining all of the IPTV accountsassociated with a message.

The mediation database 210 of the illustrated example stores informationthat associates accounts/destinations of the messaging provider(s) 108of FIG. 1 with the accounts of the IPTV system 110. The mediationdatabase 210 of the illustrated example is a database that storesrecords that associate messaging provider account identifiers (e.g.,usernames, email addresses, phone numbers, account numbers, networkaddresses, etc.) with corresponding IPTV account identifiers (e.g., anaccount number, telephone number, etc.). Alternatively, the mediationdatabase 210 may be any other type of data storage such as a file, adirectory, data stored on a hard disk drive, etc.

The provider information database 212 of the illustrated example storesinformation about the messaging provider(s) 108 and/or the format andstructure of messages associated with the messaging provider(s) 108. Forexample, the provider information database 212 may store a format (e.g.,a data encoding, etc.) of a messaging provider, a data layout (e.g., anindication of where data is stored in the message), etc. Accordingly,the provider information database 212 allows the mediation system 106 towork with multiple messaging providers that use different message mediatypes. In addition, the provider information database 212 may storeinformation about how to request notification of new messages from thedifferent messaging provider(s) 108. For example, the providerinformation database 212 may store a network location of the messagingprovider and an indication of what commands may be used to subscribe tonotifications.

The notification generator 214 receives notifications from thenotification receiver 204 and processes them to prepare them for displayon the IPTV device 102 b of FIG. 1. For example, the notificationgenerator 214 may format the notification so that it can be handled bythe notification subsystem of the IPTV system 110. To determine how tohandle notifications and determine the messaging provider accountassociated with the notification, the notification generator 214 of theillustrated example queries the provider information database 212 forinformation about notifications from the messaging provider(s) 108. Inaddition, the notification generator 214 determines the IPTV accountdestination(s) for the notification and includes the IPTV accountdestination information with the notification that is sent to the IPTVsystem 110. To determine the IPTV account destination information, thenotification generator 214 of the illustrated example queries themediation database 210 with the messaging provider account informationassociated with the notification. Persons of ordinary skill in the artwill recognize that the notification generator 214 may be integratedwith the message presenter 208 (i.e., they may be the same device).

The request receiver 216 of the illustrated example receives requestsfor message presentation from IPTV users (e.g., the user location 102).According to the illustrated example, the request may specify aparticular messaging provider for which a message summary should bepresented, a particular message that should be presented a particularmessage or group of messages that should be deleted, a particularmessage or group of messages that should be marked as read or unread, asummary of all messages from all messaging providers that should bepresented, etc. The request receiver processes the request(s) and sendsthe request(s) to the message transceiver 202. Upon receiving a requestfrom an IPTV device, the request receiver 216 queries the mediationdatabase 210 for associated messaging provider accounts and queries theprovider information database 212 for messaging provider information,including information and guidelines on presentation format. Thisinformation is bundled and sent to the messaging transceiver 202 torequest messages or other information from messaging providers. In thisexample implementation, the messaging transceiver 202 and the messageconverter 206 do not need to query the database 212 when handling formatconversion.

The administration interface 218 provides a user interface to allowconfiguration of the mediation system 106. In the illustrated example,the administration interface 218 is a webpage interface. Alternatively,the administration interface 218 may be provided by any other type ofinterface. The administration interface 218 may allow configuration ofrecords in the mediation database 210, information in the providerinformation database 212, etc. The administration interface 218 isconnected to the network 104 to allow configuration access by otherdevices connected to the network 104. Alternatively, the administrationinterface 218 may be directly connected to other devices, may bewirelessly connected to other devices, etc. The administration interface218 of the illustrated example is protected by a username and password.The administration interface 218 may additionally support secure accesschannels, such as internet protocol (IP) security (IPSec) or hyper texttransfer protocol (HTTP) over secure socket layer (SSL) (HTTPS). Theadministration interface 218 may include multiple usernames andpasswords that enable different levels of secure access to theadministration interface 218. For example, a first access level mayenable a user to modify associations between IPTV accounts and messagingprovider accounts and a second access level may enable a user to modifythe associations as well as to modify information stored in the providerinformation database 212. The administration interface 218 mayalternatively use any other type of authentication or may not use anyauthentication.

FIGS. 3-6 are flowcharts representative of example machine readableinstructions that may be executed to implement the example VoIP providersystem 105, mediation system 106, the example messaging provider(s) 108,the example IPTV system 110, and the example IPTV notificationsub-system 110 a, of the example system 100 of FIG. 1 and the messagingtransceiver 202, the notification receiver 204, the message converter206, the message presenter 208, the mediation database 210, the providerinformation database 212, the notification generator 214, the requestreceiver 216, and the administration interface 218 of the examplemediation system 106 of FIG. 2. The example machine readableinstructions of FIGS. 3-6 may be executed by a processor, a controller,and/or any other suitable processing device. For example, the examplemachine readable instructions of FIGS. 3-6 may be embodied in codedinstructions stored on a tangible medium such as a flash memory, orrandom access memory (RAM) associated with a processor (e.g., theprocessor 1012 shown in the example processor platform 1000 anddiscussed below in conjunction with FIG. 10). Alternatively, some or allof the example flowcharts of FIGS. 3-8 may be implemented using anapplication specific integrated circuit (ASIC), a programmable logicdevice (PLD), a field programmable logic device (FPLD), discrete logic,hardware, firmware, etc. In addition, some or all of the exampleflowcharts of FIGS. 3-6 may be implemented manually or as combinationsof any of the foregoing techniques, for example, a combination offirmware, software, and/or hardware. Further, although the examplemachine readable instructions of FIGS. 3-6 are described with referenceto the flowcharts of FIGS. 3-6, persons of ordinary skill in the artwill readily appreciate that many other methods of implementing theexample VoIP provider system 105, mediation system 106, the examplemessaging provider(s) 108, the example IPTV system 110, and the exampleIPTV notification sub-system 110 a, of the example system 100 of FIG. 1and the messaging transceiver 202, the notification receiver 204, themessage converter 206, the message presenter 208, the mediation database210, the provider information database 212, the notification generator214, the request receiver 216, and the administration interface 218 ofthe example mediation system 106 of FIG. 2 may be employed. For example,the order of execution of the blocks may be changed, and/or some of theblocks described may be changed, eliminated, sub-divided, and/orcombined. Additionally, persons of ordinary skill in the art willappreciate that the example machine readable instructions of FIGS. 3-6be carried out sequentially and/or carried out in parallel by, forexample, separate processing threads, processors, devices, circuits,etc.

FIG. 3 is a flowchart representative of example machine readableinstructions that may be executed to handle message notifications at themediation system 106 (e.g., notifications regarding new email messages,voicemail messages, text messages, etc.). The example machine readableinstructions of FIG. 3 begin when the notification receiver 204 of FIG.2 receives a new message notification from a messaging provider 108 ofFIG. 1 (block 302).

The example notification generator 214 then determines the message owneraccount identifier or any other identifier that identifies the messagingprovider account associated with the notification (block 304). Forexample, the notification generator 214 may parse the information in thenotification to determine a username, email address, phone number, etc.associated with the notification. Alternatively, the notificationgenerator may query an application program interface (API) for messageinformation. Using the message owner account identifier, the examplenotification generator 214 queries the mediation database 210 todetermine the IPTV account(s) associated with the message owner accountidentifier (i.e., the IPTV account(s) that should receive thenotification) (block 306).

The example notification generator 214 then determines if an IPTVaccount associated with the identifier is located in the mediationdatabase 210 (block 308). If an IPTV account was not located in themediation database 210 (block 308), the notification generator transmitsan error to the messaging provider indicating that an IPTV accountassociated with the notification was not located (block 314). Controlthen returns to block 302 to wait for the next notification from theexample messaging provider(s) 108. Alternatively, such errors may bedropped without error response to the messaging provider who sent thenotification.

If an IPTV account associated with the identifier was located in themediation database 210 (block 308), the example notification generator214 determines one or more IPTV device identifiers associated with theIPTV account (block 309). The example notification generator 214 formatsthe notification including the first IPTV device identifier forpresentation via the IPTV system 110 of FIG. 1 (block 310). Then, thenotification generator 214 of the illustrated example transmits thenotification to the IPTV system 110 (block 312). The examplenotification generator 214 then determines if another IPTV deviceidentifier was located in block 309 (block 313). If another IPTV deviceidentifier was located, control returns to block 310 to continue sendingnotifications. If another IPTV device identifier was not located (block313), control returns to block 302 to wait for the next notificationfrom the example messaging provider(s) 108.

In an alternate implementation, the IPTV system 110 and/or thenotification generator 214 may determine if the IPTV device specified bythe IPTV device identifier is set to disable notifications. If the IPTVdevice is set to disable notification, the notification message isdropped and is not presented on the IPTV device (or a connectedpresentation device).

FIG. 4 is a flowchart representative of example machine readableinstructions that may be executed to handle a request for a message listat the example mediation system 106 of FIG. 1. The example machinereadable instructions of FIG. 4 begin when the request receiver 216 ofFIG. 2 receives a request for a message list (block 402). The requestmay be for a message list from a specific messaging provider, from asubset of messaging providers, or from all available messagingproviders. The request receiver 216 then determines an IPTV accountidentifier and IPTV device identifiers associated with the request(block 404). For example, the request receiver 216 may parse the requestto determine the source of the request, may receive IPTV accountidentification information from the IPTV system 110 of FIG. 1, etc.

After determining an IPTV account identifier associated with the request(block 404), the example request receiver 216 queries the mediationdatabase 210 using the IPTV account identifier to determine one or moremessaging account identifiers associated with the IPTV account (block406). For example, the IPTV account identifier may be associated with avoicemail account, a text messaging account, and an email account. Theexample request receiver 216 then determines if a messaging accountidentifier associated with the IPTV account identifier was located(block 408). If a messaging account identifier was not located, therequest receiver 216 sends an error notification to the IPTV system 110(block 416). Control then returns to block 402 to wait for the nextrequest.

If one or more of messaging account identifier(s) were located (block408), the example request receiver 216 sends a request to the firstmessage provider associated with the located messaging accountidentifier(s) requesting a message list via the corresponding messagingtransceiver 202 (block 410). The messaging transceiver 202 then receivesmessage list(s) from the messaging provider(s) and sends the receivedmessage list(s) to the message presenter 208 via the message converter206 (block 411). Alternatively, the messaging transceiver 202 may sendsome messages to the message presenter 208 if conversion is not desired.

The example message presenter 208 then determines if there are furthermessaging providers associated with the located message accountidentifier(s) (e.g., a second message provider associated with a secondone of the message account identifiers) (block 415). If there arefurther messaging providers associated with the located message accountidentifier(s), control returns to block 410 to continue requestingmessage lists. The message presenter 208 may query the providerinformation database 212 for more details on the presentation format.Alternatively, some presentation guidelines can be stored in the messagepresenter 208 in the form of XML style sheet definitions. If there areno further messaging providers, the message presenter 208 receives themessage list(s) and generates a presentation of the message list(s) tobe presented via the IPTV system 110 (block 413). The example messagepresenter 208 then transmits the message list presentation to the IPTVsystem 110 for presentation at the user location 102 (block 414).Control then returns to block 402 to wait for the next request.

In an alternate implementation, the example message presenter 208 maysend a message list from each messaging provider as they are received,rather than aggregating the message list.

FIG. 5 is a flowchart representative of example machine readableinstructions that may be executed to handle a request for messagepresentation at the example mediation system 106 of FIG. 1. The examplemachine readable instructions of FIG. 5 begin when the request receiver216 of FIG. 2 receives a request for message presentation (block 502).The request receiver 216 then determines a message identifier and anIPTV account identifier associated with the request (block 504). Forexample, the request receiver 216 may parse the request to determine thesource of the request, may receive IPTV account identificationinformation from the IPTV system 110 of FIG. 1, etc. In addition, theexample request receiver 216 may parse the request to determine anidentifier associated with the requested message. Additionally oralternatively, the example request receiver 216 may query the providerinformation database 212 with information from the request to determinethe identity of the requested message.

After determining an IPTV account identifier and message identityassociated with the request (block 504), the example request receiver216 queries the mediation database 210 to determine the messagingprovider who has the requested message (block 506). The request receiver216 also queries for guidelines on format conversion, for example, themessage from a message provider may be in MP3, and need to converted tothe WMA format before being presented to the IPTV. For example, the IPTVaccount identifier may be associated with a voicemail account, a textmessaging account, and/or an email account. The example request receiver216 then determines if a messaging provider identifier associated withthe IPTV account identifier was located (block 508). If a messagingprovider identifier was not located (block 508), the request receiver216 sends an error notification to the IPTV system 110 (block 520).Control then returns to block 502 to wait for the next request.

If a messaging provider identifier was located (block 508), the examplerequest receiver 216 converts the received message identifier into aprovider specific message identifier (e.g., a number that references themessage on the system of the messaging provider (block 510). The requestreceiver then sends a request for the message to the messaging providerassociated with the message via the messaging transceiver 202 (block512).

The messaging transceiver 202 then receives the requested message fromthe messaging provider associated with the message and sends thereceived message to the message converter 206 (block 513). The examplemessage converter 206 converts the message to make the message suitablefor display via the IPTV system 110 (block 514). Then, the examplemessage presenter 208 generates a presentation for the converted message(block 516). For example, the message presenter 208 may generate agraphical display, an audible presentation, a video display, etc. Then,the example message presenter 208 sends the generated presentation tothe IPTV system 110. Control then returns to block 502 to wait for thenext request.

Persons of ordinary skill in the art will recognize that when multiplemessages are requested, the example mediation system 106 may iterateover the set of requested messages.

FIG. 6 is a flowchart representative of example machine readableinstructions that may be executed to handle a request for messagedeletion at the example mediation system 106 of FIG. 1. The examplemachine readable instructions of FIG. 6 begin when the request receiver216 of FIG. 2 receives a request for message deletion (block 602). Therequest receiver 216 then determines a message identifier and an IPTVaccount identifier associated with the request (block 604). For example,the request receiver 216 may parse the request to determine the sourceof the request, may receive IPTV account identification information fromthe IPTV system 110 of FIG. 1, etc. In addition, the example requestreceiver 216 may parse the request to determine an identifier associatedwith the requested message. Additionally or alternatively, the examplerequest receiver 216 may query the provider information database 212with information from the request to determine the identity of therequested message.

After determining an IPTV account identifier associated with therequest, the example request receiver 216 queries the mediation database210 using the IPTV account identifier and the message identifier todetermine a messaging provider associated with the message to be deleted(block 606). For example, the IPTV account identifier may be associatedwith a voicemail account, a text messaging account, and/or an emailaccount. The example request receiver 216 then determines if a messagingprovider identifier associated with the IPTV account identifier waslocated (block 608). If a messaging provider identifier was not located,the request receiver 216 sends an error notification to the IPTV system110 (block 618). Control then returns to block 502 to wait for the nextrequest.

If a messaging provider identifier was located (block 608), the examplerequest receiver 216 converts the received message identifier into aprovider specific message (e.g., a number that references the message onthe system of the messaging provider (block 610). The request receiverthen sends a request for message deletion to the messaging providerassociated with the message via the messaging transceiver 202 (block612).

The messaging transceiver 202 then receives confirmation of deletion ofthe message from the messaging provider associated with the message andsends the confirmation to the message presenter 208 via the messageconverter 206 (block 614). Then, the example message presenter 208generates a presentation for the confirmation (block 616). For example,the message presenter 208 may generate a graphical display, an audiblepresentation, a video display etc. Then, the example message presenter208 sends the generated presentation to the IPTV system 110 (block 616).Control then returns to block 602 to wait for the next request.Alternatively, the IPTV system 110 may remove the deleted message fromthe message lists display.

Persons of ordinary skill in the art will recognize that when multiplemessages are requested, the example mediation system 106 may iterateover the set of requested messages.

FIG. 7 is a flowchart representative of example machine readableinstructions that may be executed to handle a request for a message listsummary (e.g., a summary of the message status at one or more messagingproviders such as, 5 new messages, 2 unread messages, 40 total messages)at the example mediation system 106 of FIG. 1. The example machinereadable instructions of FIG. 7 begin when the request receiver 216 ofFIG. 2 receives a request for a message list summary (block 702). Therequest may be for a message list summary from a specific messagingprovider, from a subset of messaging providers, or from all availablemessaging providers. The request receiver 216 then determines an IPTVaccount identifier and IPTV device identifiers associated with therequest (block 704). For example, the request receiver 216 may parse therequest to determine the source of the request, may receive IPTV accountidentification information from the IPTV system 110 of FIG. 1, etc.

After determining an IPTV account identifier associated with the request(block 704), the example request receiver 216 queries the mediationdatabase 210 using the IPTV account identifier to determine one or moremessaging account identifiers associated with the IPTV account (block706). For example, the IPTV account identifier may be associated with avoicemail account, a text messaging account, and an email account. Theexample request receiver 216 then determines if a messaging accountidentifier associated with the IPTV account identifier was located(block 708). If a messaging account identifier was not located, therequest receiver 216 sends an error notification to the IPTV system 110(block 716). Control then returns to block 702 to wait for the nextrequest.

If one or more of messaging account identifier(s) were located (block708), the example request receiver 216 sends a request to the firstmessage provider associated with the located messaging accountidentifier(s) requesting a message list summary via the correspondingmessaging transceiver 202 (block 710). The messaging transceiver 202then receives message list summary(s) from the messaging provider(s) andsends the received message list summary(s) to the message presenter 208via the message converter 206 (block 711). The example message presenter208 then determines if there are further messaging providers associatedwith the located message account identifier(s) (e.g., a second messageprovider associated with a second one of the message accountidentifiers) (block 712). If there are further messaging providersassociated with the located message account identifier(s), controlreturns to block 710 to continue requesting and sending message listsummaries.

If there are no further messaging providers (block 712), the examplemessage presenter 208 receives the message list summary(s) and generatesa presentation of the message list summary(s) to be presented via theIPTV system 110 (block 713). The example message presenter 208 thentransmits the message list summary presentation to the IPTV system 110for presentation at the user location 102 (block 714). Control thenreturns to block 702 to wait for the next request.

In an alternate implementation, the message list summary may include asummary for each provider (including the name of the provider in thesummary), a summary for each type of provider (e.g., all voicemailmessages are summarized in one summary and all emails are summarized ina second summary), a summary for all providers, etc. Alternatively, anapplication in the IPTV 102 b may run in the background to request themessage list summary periodically and update a footnote presentation onthe TV screen.

FIG. 8 is a flowchart representative of example machine readableinstructions that may be executed to handle a request for a contact list(e.g., an address book or any other list of messaging contacts) at theexample mediation system 106 of FIG. 1. The example machine readableinstructions of FIG. 8 begin when the request receiver 216 of FIG. 2receives a request for a contact list (block 802). The request may befor a contact list from a specific messaging provider, from a subset ofmessaging providers, or from all available messaging providers. Therequest receiver 216 then determines an IPTV account identifier and IPTVdevice identifiers associated with the request (block 804). For example,the request receiver 216 may parse the request to determine the sourceof the request, may receive IPTV account identification information fromthe IPTV system 110 of FIG. 1, etc.

After determining an IPTV account identifier associated with the request(block 804), the example request receiver 216 queries the mediationdatabase 210 using the IPTV account identifier to determine one or moremessaging account identifiers associated with the IPTV account (block806). For example, the IPTV account identifier may be associated with avoicemail account, a text messaging account, and an email account. Theexample request receiver 216 then determines if a messaging accountidentifier associated with the IPTV account identifier was located(block 808). If a messaging account identifier was not located, therequest receiver 216 sends an error notification to the IPTV system 110(block 816). Control then returns to block 802 to wait for the nextrequest.

If one or more of messaging account identifier(s) were located (block808), the example request receiver 216 sends a request to the one ormore message providers associated with the located messaging accountidentifier(s) requesting a contact list via the corresponding messagingtransceiver 202 (block 810). The messaging transceiver 202 then receivesone or more contact list(s) from the messaging provider(s) and sends thereceived contact list(s) to the message presenter 208 via the messageconverter 206 (block 811). The example request receiver 216 thendetermines if there are further messaging providers identified by themessaging account identifier(s) (block 812). If there are furthermessaging providers, control returns to block 810 to continue requestingcontact lists.

If there are no further messaging providers (block 812), the examplemessage presenter 208 receives the contact list(s), aggregates allreceived contact lists into a single aggregate contact list, andgenerates a presentation of the aggregate contact list to be presentedvia the IPTV system 110 (block 813). The example message presenter 208then transmits the aggregate contact list presentation to the IPTVsystem 110 for presentation at the user location 102 (block 814).

In an alternate implementation, the message presenter 208 may notaggregate that the received contacts lists. Rather, the messagepresenter 208 may process each contact list for presentationindividually.

FIG. 9 illustrates an example data schema 900 that illustrates howmessaging accounts may be linked to IPTV devices via an IPTV externalidentifier. The message accounts 902 include a service policy 906, aservice profile 908, and an account identifier 910. In the illustratedexample, a VoIP account, a time division multiplexing (TDM) account, andtwo wireless accounts. The service policy 906 defines features that canbe used by a user of the particular message account and/or how thosefeatures may be used (e.g., call forwarding may be enabled by amessaging provider, but may be disabled by a user to prevent its use).The service profile 908 defines what features are enabled for aparticular messaging account. The account identifier 910 provides aunique identification for a particular messaging account (e.g., a phonenumber).

The IPTV external identifier 904 is a unique identifier for a particularIPTV account. The IPTV external identifier 904 is linked to one or moremessage accounts (e.g., linked in the mediation database 210 of FIG. 2).The IPTV external identifier 904 may be associated with multiple IPTVdevice (e.g., multiple devices at multiple locations in a consumerhousehold). The IPTV external identifier is linked to a deviceidentifier 912 (e.g., a set top box device identifier) for each IPTVdevice. The device identifier 912 is linked to an IPTV service profile914 for the IPTV device. The IPTV service profile 914 defines thefeatures that are available from a provider for a particular IPTV device(e.g., digital video recording capabilities, channel packages that areenabled, pay per view purchasing, etc.). The IPTV service profile 914 islinked to an IPTV service policy 916 for associated the IPTV device. TheIPTV service policy 916 defines which features are enabled for aparticular IPTV device. For example, the IPTV service policy 916 mayspecify that message presentation is disabled for a particular device,even though message presentation is enabled for the IPTV account andmessage presentation is available at other IPTV devices. The IPTVService profile 914 may contain the content presentation formatinformation, for example, a list of supported audio formats (e.g., WAV,WMA, etc.), a text presentation style definition, etc. The IPTV servicepolicy 914 may additionally include information such as a setting forenabling or disabling new message notification, a setting for enablingor disabling message list summary presentation, etc.

FIG. 10 is a block diagram of an example computer 1000 capable ofexecuting the machine readable instructions illustrated in FIGS. 3 to 10to implement the mediation system 106 and/or the other apparatus and/ormethods disclosed herein.

The system 1000 of the instant example includes a processor 1012 such asa general purpose programmable processor. The processor 1012 includes alocal memory 1014, and executes coded instructions 1016 present inrandom access memory 1018, coded instruction 1017 present in the readonly memory 1020, and/or instructions present in another memory device.The processor 1012 may execute, among other things, the machine readableinstructions represented in FIGS. 3 to 8. The processor 1012 may be anytype of processing unit, such as a microprocessor from the Intel®Centrino® family of microprocessors, the Intel® Pentium® family ofmicroprocessors, the Intel® Itanium® family of microprocessors, and/orthe Intel XScale® family of processors. Of course, other processors fromother families are also appropriate.

The processor 1012 is in communication with a main memory including avolatile memory 1018 and a non-volatile memory 1020 via a bus 1025. Thevolatile memory 1018 may be implemented by Synchronous Dynamic RandomAccess Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUSDynamic Random Access Memory (RDRAM) and/or any other type of randomaccess memory device. The non-volatile memory 1020 may be implemented byflash memory and/or any other desired type of memory device. Access tothe main memory 1018, 1020 is typically controlled by a memorycontroller (not shown) in a conventional manner.

The computer 1000 also includes a conventional interface circuit 1024.The interface circuit 1024 may be implemented by any type of well knowninterface standard, such as an Ethernet interface, a universal serialbus (USB), and/or a third generation input/output (3GIO) interface.

One or more input devices 1026 are connected to the interface circuit1024. The input device(s) 1026 permit a user to enter data and commandsinto the processor 1012. The input device(s) can be implemented by, forexample, a keyboard, a mouse, a touchscreen, a track-pad, a trackball,isopoint and/or a voice recognition system.

One or more output devices 1028 are also connected to the interfacecircuit 1024. The output devices 1028 can be implemented, for example,by display devices (e.g., a liquid crystal display, a cathode ray tubedisplay (CRT), a printer and/or speakers). The interface circuit 1024,thus, typically includes a graphics driver card.

The interface circuit 1024 also includes a communication device such asa modem or network interface card to facilitate exchange of data withexternal computers via a network (e.g., an Ethernet connection, adigital subscriber line (DSL), a telephone line, coaxial cable, acellular telephone system, etc.).

The computer 1000 also includes one or more mass storage devices 1030for storing software and data. Examples of such mass storage devices1030 include floppy disk drives, hard drive disks, compact disk drivesand digital versatile disk (DVD) drives.

At least some of the above described example methods and/or apparatusare implemented by one or more software and/or firmware programs runningon a computer processor. However, dedicated hardware implementationsincluding, but not limited to, application specific integrated circuits,programmable logic arrays and other hardware devices can likewise beconstructed to implement some or all of the example methods and/orapparatus described herein, either in whole or in part. Furthermore,alternative software implementations including, but not limited to,distributed processing or component/object distributed processing,parallel processing, or virtual machine processing can also beconstructed to implement the example methods and/or apparatus describedherein.

It should also be noted that the example software and/or firmwareimplementations described herein are optionally stored on a tangiblestorage medium, such as: a magnetic medium (e.g., a magnetic disk ortape); a magneto-optical or optical medium such as an optical disk; or asolid state medium such as a memory card or other package that housesone or more read-only (non-volatile) memories, random access memories,or other re-writable (volatile) memories; or a signal containingcomputer instructions. A digital file attached to e-mail or otherinformation archive or set of archives is considered a distributionmedium equivalent to a tangible storage medium. Accordingly, the examplesoftware and/or firmware described herein can be stored on a tangiblestorage medium or distribution medium such as those described above orsuccessor storage media.

Although this patent discloses example systems including software orfirmware executed on hardware, it should be noted that such systems aremerely illustrative and should not be considered as limiting. Forexample, it is contemplated that any or all of these hardware andsoftware components could be embodied exclusively in hardware,exclusively in software, exclusively in firmware or in some combinationof hardware, firmware and/or software. Accordingly, while the abovespecification described example systems, methods and articles ofmanufacture, persons of ordinary skill in the art will readilyappreciate that the examples are not the only way to implement suchsystems, methods and articles of manufacture. Therefore, althoughcertain example methods, apparatus and articles of manufacture have beendescribed herein, the scope of coverage of this patent is not limitedthereto. On the contrary, this patent covers all methods, apparatus andarticles of manufacture fairly falling within the scope of the appendedclaims either literally or under the doctrine of equivalents.

1. A method to provide voicemail messages to a television user, the method comprising: receiving a request to access a voicemail account from the television user; determining a voicemail mailbox associated with the television user; and sending at least one of a list of one or more voicemail messages or a voicemail message to a display device associated with the television user.
 2. A method as defined in claim 1, wherein the television user is an internet protocol television user.
 3. A method as defined in claim 1, wherein the voicemail mailbox is a voicemail mailbox associated with at least one of a voice over internet protocol service, a mobile phone service, or a public switched telephone network service.
 4. A method as defined in claim 1, wherein sending the at least one of a list of one or more voicemail messages or the voicemail message to the display device associated with the television user is performed using a terminal session.
 5. A method as defined in claim 4, wherein the terminal session is a remote desktop session.
 6. A method as defined in claim 1, further comprising determining an account identifier associated with the television user.
 7. A method as defined in claim 6, further comprising determining a voicemail mailbox associated with the account identifier.
 8. A method as defined in claim 1, further comprising converting the voicemail message from a first format to a second format before sending the voicemail message to the television user.
 9. A method as defined in claim 1, further comprising generating a graphical user interface associated with the list of one or more voicemail messages.
 10. (canceled)
 11. (canceled)
 12. (canceled)
 13. (canceled)
 14. (canceled)
 15. (canceled)
 16. (canceled)
 17. (canceled)
 18. (canceled)
 19. (canceled)
 20. (canceled)
 21. (canceled)
 22. (canceled)
 23. (canceled)
 24. (canceled)
 25. (canceled)
 26. (canceled)
 27. (canceled)
 28. (canceled)
 29. (canceled)
 30. An article of manufacture storing machine readable instructions which, when executed, cause a machine to: receive a request to access a voicemail account from a television user; determine a voicemail mailbox associated with the television user; and send at least one of a list of one or more voicemail messages or a voicemail message to a display device associated with the television user.
 31. An article of manufacture as defined in claim 30, wherein the television user is an internet protocol television user.
 32. An article of manufacture as defined in claim 30, wherein the voicemail mailbox is a voicemail mailbox associated with at least one of a voice over internet protocol service, a mobile phone service, or a public switched telephone network service.
 33. An article of manufacture as defined in claim 30, wherein sending the at least one of a list of one or more voicemail messages or the voicemail message to the display device associated with the television user is performed using a terminal session.
 34. An article of manufacture as defined in claim 21, wherein the terminal session is a remote desktop session.
 35. An article of manufacture as defined in claim 30, wherein the machine readable instructions further cause the machine to determine an account identifier associated with the television user.
 36. An article of manufacture as defined in claim 35, wherein the machine readable instructions further cause the machine to determine a voicemail mailbox associated with the account identifier.
 37. An article of manufacture as defined in claim 30, wherein the machine readable instructions further cause the machine to convert the voicemail message from a first format to a second format before sending the voicemail message to the television user.
 38. An article of manufacture as defined in claim 30, wherein the machine readable instructions further cause the machine to generate a graphical user interface associated with the list of one or more voicemail messages.
 39. (canceled)
 40. (canceled)
 41. (canceled)
 42. (canceled)
 43. (canceled)
 44. (canceled)
 45. (canceled)
 46. (canceled)
 47. (canceled)
 48. (canceled)
 49. (canceled)
 50. (canceled)
 51. (canceled)
 52. (canceled)
 53. (canceled)
 54. An apparatus for providing voicemail messages to a television user, the apparatus comprising: a database associating an identifier associated with a television device with a voicemail mailbox; a request receiver to receive a request for a list of voicemail message information from a television device, to determine the identifier associated with the television device, to query the database to determine the voicemail mailbox associated with the identifier; and a message presenter to initiate a terminal session with the television device and send the list of voicemail message information to the television device via the terminal session.
 55. An apparatus as defined in claim 54, wherein the request receiver is further to determine an electronic mail mailbox associated with the identifier.
 56. An apparatus as defined in claim 55, further comprising a messaging transceiver to retrieve an electronic mail message from the electronic mail mailbox, wherein the message presenter is further to send the electronic mail message to the television device via the terminal session.
 57. An apparatus as defined in claim 54, further comprising a notification generator to send a notification to the television device indicating that a new voicemail message has been placed in the voicemail mailbox.
 58. An apparatus as defined in claim 57, further comprising: a notification receiver to receive a notification that a new voicemail message is available at a message provider, wherein the notification generator is further to send a notification to the television device, the notification indicating that a new voicemail message is available.
 59. An apparatus as defined in claim 58, wherein the request is responsive to the notification.
 60. An apparatus as defined in claim 54, wherein the television device is an internet protocol television device.
 61. An apparatus as defined in claim 54, wherein the message presenter is further to send a list of electronic mail message information with the list of voicemail message information, the list of voicemail message information being associated with a user of the television device.
 62. An apparatus as defined in claim 54, further comprising an administration interface to allow a user to modify the database.
 63. An apparatus as defined in claim 54, wherein the database is further to provide information associated with the voicemail message provider. 